chore(pmm-fb): repin both halves of the feature build - #1461
Merged
Conversation
Both PMM_FB_TAG defaults move from PR-4500-a2f83c2 (2026-08-25) to PR-4500-2c43912, cut 2026-09-03 from percona/pmm PMM-15205-sep-fb @ 53521917d. The harness was two builds behind - PR-4500-d85ca73 also came and went. What the new build carries that a2f83c2 did not: PMM-15205-sep-fb was rebuilt as linear per-ticket history on main, and percona/pmm#5759 (the /sep/ nginx reverse proxy), #5762 (SEP's secret files and generated database password) and #5886 (the vendored SEP frontend synced to SEP main c16578d) have all merged into it. The side-car pin is deliberately left at 249f673. Nothing at or after c16578d is published, so there is no image to move to - the newest tag on percona/percona-sep is the one already pinned. That leaves the pair mismatched, PMM-new against SEP-old, and the three newly ported frontend features degrade rather than break: - Support-case autocomplete issues no requests at all. It is gated on case_search_available from atw_config, which this side-car does not send, so the field stays a plain text input. - The executor co-location warning never mounts: it needs target_service on the host field's schema, which this side-car does not declare. - The unlaunchable status never arrives, so its badge is simply unused. Exercising any of those needs a side-car built at or after c16578d. The stale-status crash fix in #5886 is not affected - stale predates all of this and this build fixes it against any side-car. Claude-Session: https://claude.ai/code/session_01RFUiQUpHgyaK6ozEQJ8wmT Signed-off-by: Yan Orestes <yan.orestes@percona.com>
yyyyyyyan
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Moves both halves of
sidecar/pmm-fb/compose.yamlforward together.pmm-server—PMM_FB_TAG, both defaultsPR-4500-a2f83c2(2026-08-25)PR-4500-2c43912— cut 2026-09-03 from percona/pmmPMM-15205-sep-fb@ 53521917dsep-sidecarmain's tip, published 2026-09-04 by JenkinsSEP/Build#235The PMM half was two builds behind —
PR-4500-d85ca73also came and went.What the new PMM build carries
PMM-15205-sep-fbwas rebuilt as linear per-ticket history onmain, and three PRs have merged into it since a2f83c2:/sep/nginx reverse proxy, productized out of this harness's overlaymainc16578dThe side-car moves with it
This PR originally held
sep-sidecarat 249f673, because nothing at or after c16578d had been published and there was no image to move to. That left the pair mismatched, PMM-new against SEP-old.It no longer is.
mainwas merged intopmmas 1efbbe8, andSEP/Build#235 publishedmain's tip — 62 commits on from the old pin. c16578d is an ancestor of it, so the frontend sync in percona/pmm#5886 now has a side-car that answers it.The three features that would have degraded are live instead. Each symbol is present under
app/at b97ee98 and absent at 249f673:case_search_availablefromatw_config, which this side-car sends.target_serviceon the host field's schema, which this side-car declares.unlaunchablestatus (SEP-1943) arrives, so its badge is exercised rather than unused.Tested
Both pins were resolved against Docker Hub before merge:
perconalab/pmm-server-fb:PR-4500-2c43912(pushed 2026-09-03) andpercona/percona-sep:b97ee985fc64f841f611b3a057737814da308a61(pushed 2026-09-04).The side-car image was then held against the three repin checks the harness README requires on the artifact rather than on the commit that built it:
SECRETS_DIRreferences insettings-env.shgrafana_service_account.pypresent; the image'sstatedirectory isdrwx------ sep sepHEALTHCHECK, read from the raw config blobCMDrunshealthcheck.sh, start period 150 sNo paired bring-up was run — this is a two-line pin change, and the artifact checks are what the README asks for at repin time.
Checklist
make test)make run-pre-commit)make makemigrations)changelog.d/if the change is user-facing (make changelog-add), or confirmed N/A (internal-only change, or a same-release-cycle fix for an unreleased sibling ticket)